Alerts
Archeo's alert system enables users to receive notifications based on various scenarios driven by search logic. Alerts can be triggered by specific events, such as the logging of a particular status, the generation of excessive messages by an integration flow, or the occurrence of non-events. A typical non-event could be the absence of any transactions over the past 6 hours, prompting an alert notification.
Create Alert
To create an alert based on a search, first configure your search with all the necessary parameters. Once set, simply click on 'Create alert from search parameters' located in the 'burger' menu at the top right corner.
This will open the Alert form with all the parameters pre-filled, or open a new form from the "Administration Alerts" main menu item.
Alert Name and description
| Property | Description |
|---|---|
| Name* | The name of the alert, we recommend giving the alert a descriptive name, like "Error on orders from Salesforce" |
| Description | The description of the alert |
(* Mandatory)
Alert filters
| Filter | Description |
|---|---|
| File content | A word or phrase from the file content |
| Transaction Tag | Explicit search for the logged transaction tag |
| Transaction type | Dropdown with available transaction types. Filters transactions based on selection |
| Message type | Dropdown with available message types. Filters transactions based on selection |
| Sender | Dropdown with available senders. Filters transactions based on selection |
| Receiver | Dropdown with available receivers. Filters transactions based on selection |
| Status | Dropdown with available statuses. Filters transactions based on selection |
Alert Conditions
| Condition | Description |
|---|---|
| Logical operator | The operator used to compare the result value against the threshold |
| Threshold | A value to trigger the alert |
| Timeout | This value determines how long the alert should wait after an alert is triggered before a new alert should be triggered. If frequency is set to 15 min and timeout is set to 1 hour, alerts will be triggered at most every hour. |
| Period | Dropdown with available message types. Filters transactions based on selection |
| Frequency | Dropdown with available senders. Filters transactions based on selection |
| Enable timeout override | Override the timeout if an override threshold is reached. Makes the "Timeout override threshold" condition visible |
| Timeout override threshold | The threshold for when to override the timeout. If this threshold is reached during a timeout, a new alert will be triggered. If frequency is set to 15 min and timeout is set to 1 hour, and “timeout override threshold” is set to 50. If the threshold of 50 is met, it will override the timeout and send an alert. This is a handy way to discover when things have gone really bad regardless of the timeout. |
Distribution Channel
This is how the alerts are distributed. For now, we support e-mail and webhooks. To add Email-groups or webhooks, see the section about email groups and webhooks . When an alert is triggered everyone on the e-mail group will receive an e-mail, with link to open search view with result that triggered the alert.
Save and enable
Use the chekbox "Enable Alert" to Enable/Disable the alert. The "Save" button saves the alert and "Close" closes the form without saving.
Manage Alerts
All alerts are listed in the main form. Here you are able to activate/deactivate, edit or delete the alert.
Alert log
All generated alerts are listed with details, to give the full overview including link to the logs creating the alert.
| Column | Description |
|---|---|
| Trigger time | Date and time of when the alert was generated |
| Threshold | The set threshold for this alert |
| Hits | Number of hits for the result creating the alert |
| Distributed by | What distribution channels were used |
| "Link" | A direct link to search result showing the items that created this alert |
